Migrate XCO from TPVM to OVA

You can migrate XCO from TPVM-based deployment to OVA-based deployment model.

Before you begin

Ensure that no sub-interfaces, static IPs, or virtual routes are present before migration. If there are, ensure that you have deleted and re-added after migration.

About this task

Follow this process to migrate XCO from TPVM-based deployment to OVA-based deployment model.

Use the XCO backup and restore procedure to migrate XCO from TPVM High Availability to OVA single node, which will run XCO to manage a fabric with a large number of POs and EPGs.

Note

It takes approximately 1 hour to complete the migration.
As a best practice, complete the migration during a maintenance window.

Procedure

Back up XCO.
Run the following command to take a backup of the XCO config from the old TPVM (for example, EFA 2.7.2):
```
efa system backup
```
Fresh deploy OVA.
Fresh deploy single node OVA VM with the target version (for example, XCO 3.3.1).
For details on installing XCO using OVA, see Install Fabric using OVA.
Copy the backup.
Copy the backup taken from TPVM to the OVA VM location /var/log/efa/backup/:
```
cd /var/log/efa/backup/
```
Restore the backup.
Run the following command and select the backup file name which was taken from the TPVM setup:
```
efa system restore
```
Enable secure connection.
Run the following command to install the certificates on devices:
```
efa certificate device install --force
```
The command installs the HTTPS or OAuth2 certificate on one or more devices.
Verify the device status.
Run the following command to get the current state of the devices:
```
efa inventory device update
```
Stop old XCO services on TPVM.
Run the following command on both SLX switches to power off the old TPVMs where XCO is installed:
```
tpvm stop
```
Alternatively, run the following command to disable all services:
```
efactl stop
```

Results

Once the migration process is complete, the XCO IP will be replaced with the newly deployed OVA VM IP.